works with Xcode Beta 8 thank you

The same error still exists in Xcode 14.3 RC

The same error exists in Xcode 14.3 Beta 3

Thanks for you help Quinn

Finally I found my issue! It was not on signing issues at all. In release builds I generally set GCC_SYMBOLS_PRIVATE_EXTERN = NO But I forgot to flag all the exported functions with __attribute__((visibility("default")))

This is the SampleCode https://developer.apple.com/documentation/coreaudio/creating_an_audio_server_driver_plug-in which I used to start our project

This is the output: Identifier=com.teamviewer.remoteaudiodriver Format=bundle with Mach-O thin (x86_64) CodeDirectory v=20400 size=996 flags=0x0(none) hashes=24+3 location=embedded Hash type=sha256 size=32 CandidateCDHash sha256=d83384726d17e69c79a535ccc8d9e85c1d03d9b8 CandidateCDHashFull sha256=d83384726d17e69c79a535ccc8d9e85c1d03d9b882f95b4f6b65462a1a69725a Hash choices=sha256 CMSDigest=d83384726d17e69c79a535ccc8d9e85c1d03d9b882f95b4f6b65462a1a69725a CMSDigestType=2 CDHash=d83384726d17e69c79a535ccc8d9e85c1d03d9b8 Signature size=9101 Authority=Apple Development: schmitt@teamviewer.com (G76JWMDJNT) Authority=Apple Worldwide Developer Relations Certification Authority Authority=Apple Root CA Timestamp=24. Mar 2021 at 00:40:32 Info.plist entries=22 TeamIdentifier=LM497G94SC Sealed Resources version=2 rules=13 files=2 Internal requirements count=1 size=204

That is the case, but we have not understood why. The two affected frameworks had no target-dependent code. If we build from a clean state in a "combined" goal with all 5 goals, everything is fine. If we create and work on 1 target, we will later get the error when we create another target. So there must be something that causes the build system to re-create the frameworks with a different hash in the name. Then we get the error from the fast compiler.

You mean after switching from one target to an other?When we do it works but we want to avoid this because of the building time (20 min on iMac Pro / 45 min on MacBook Pro).There is no diffence in the code from the framework / modules so it should not needed to rebuild.The question is. Why does the new build system build the modules twice? This only happens for the swift compiler.

It looks like there is a connection to the new build system. We have another project with a similar structure that works without problems. The big difference is the build system